DO NOT MERGE: verify process E2E CI job split#24285
Draft
vitkyrka wants to merge 2 commits into
Draft
Conversation
vitkyrka
added
the
qa/skip-qa
|
Verification-only change to confirm the process-discovery E2E environment runs as its own separate CI job when a PR only touches krakend files. Not meant to be merged.
vitkyrka
force-pushed
the
vitkyrka/verify-process-e2e-ci-split
branch
from
9dc8f78 to
563f836
Compare
3 tasks
Contributor
Validation ReportAll 21 validations passed. Show details
|
vitkyrka
force-pushed
the
vitkyrka/disco-config-process
branch
4 times, most recently
from
377010f to
cbbf8e2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Intentionally breaks the krakend process-autodiscovery CEL selector (
process.name == 'krakend-this-will-never-match') so the process-discovery E2E test fails.Motivation
Verification-only PR to confirm that a change touching only
krakend/files (no shareddatadog_checks_dev/datadog_checks_basecode) causes the dynamic per-changed-target CI workflow to run, and that it now surfaces thepy3.13-2.10-processmatrix combination as its own separate CI job/check (rather than being folded into a singleKrakenDjob). Base isvitkyrka/disco-config-process(#24238) since this depends on the hatch.toml matrix split introduced there.Not meant to be merged — will be closed once CI is confirmed.
Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged